Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1627

reference
380-tree-1
name
1627
tree-preservation-order

undefined

380-tpo-1
uprn
address-text
point
POINT (-1.026133 50.884811)
geometry
MULTIPOLYGON (((-1.026077 50.884805,-1.026079 50.884816,-1.026087 50.884827,-1.026100 50.884835,-1.026115 50.884840,-1.026133 50.884842,-1.026150 50.884840,-1.026166 50.884835,-1.026179 50.884827,-1.026187 50.884817,-1.026190 50.884806,-1.026188 50.884795,-1.026180 50.884785,-1.026168 50.884777,-1.026152 50.884772,-1.026134 50.884770,-1.026117 50.884771,-1.026101 50.884776,-1.026088 50.884784,-1.026080 50.884794,-1.026077 50.884805)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL